|
|
Hi Peter, Additionally, Please also check "avc: denied" log. This log is being print at 1 second intervals,. 02-23 18:37:20.032 3202 3202 E SELinux : avc: denied { find } for interface=vendor.amlogic.hardware.remotecontrol::IRemoteControl sid=u:r:hal_audio_default:s0 pid=3488 scontext=u:r:hal_audio_default:s0 tcontext=u:object_r:remotecontrol_hwservice:s0 tclass=hwservice_manager permissive=0 Thank you. Kim |
|
|
Hi JunGyu, Can you share the full log for this issue? Thanks, Peter |
|
|
Hi Peter, I attached full log file. Please check it. Thank you Kim |
|
|
Hi Peter, Please let me know any update of this issue. Thank you. Kim |
|
|
Hi JunGyu, It's look like the audio input device is not correct. It will set audio input device for NUGU when RCU BT connected but sometimes it's too late to add the audio input device for NUGU. I fixed this issue with checking the audio input device is added for NUGU. Thanks, Peter |
|
|
Hi Peter, Thanks for explanation. I will let you know if any problem. I have one question, the denied message was also fixed? This log is printing too much. 02-23 18:37:20.032 3202 3202 E SELinux : avc: denied { find } for interface=vendor.amlogic.hardware.remotecontrol::IRemoteControl sid=u:r:hal_audio_default:s0 pid=3488 scontext=u:r:hal_audio_default:s0 tcontext=u:object_r:remotecontrol_hwservice:s0 tclass=hwservice_manager permissive=0 Thank you. Kim |
|
|
Hi JunGyu, The denied message has been existed from ATV10, it's useless. Thanks, Peter |
|
|
Hi Peter, Our QA tested this issue but this issue is still reproducing. The reproduce step is not clear. I checked the log and the device id is changing as below. // press NUGU 03-15 16:21:07.230 3810 3946 D WindowManager: keycode : 396 - processed. by skb function key // input device is changed 03-15 16:21:07.246 7938 7966 D audio_hw_primary: adev_open_input_stream: enter: devices(0x80000080) channel_mask(0xc) rate(48000) format(0x1) source(1) 03-15 16:21:07.257 7938 7966 D audio_hw_primary: adev_open_input_stream: enter: devices(0x90000000) channel_mask(0xc) rate(48000) format(0x3) source(1) I attached full log file. Please check it again. Thank you. Kim |
|
|
Hi JunGyu, I check the log and the input device is correct before the audio service crashed. Please check how to reproduce this. // audio input device is correct 03-15 16:20:43.270 3513 3557 D audio_hw_primary: adev_open_input_stream: enter: devices(0x80000010) channel_mask(0x10) rate(16000) format(0x1) source(20) --------- beginning of crash 03-15 16:21:05.432 7914 7914 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 03-15 16:21:05.432 7914 7914 F DEBUG : Build fingerprint: 'SKB/BFX_AT100/BFX-AT100:12/STTC.220724.001/15.537.24-20230315:userdebug/release-keys' 03-15 16:21:05.432 7914 7914 F DEBUG : Revision: '0' 03-15 16:21:05.432 7914 7914 F DEBUG : ABI: 'arm' 03-15 16:21:05.432 7914 7914 F DEBUG : Timestamp: 2023-03-15 16:21:05.289296453+0900 03-15 16:21:05.432 7914 7914 F DEBUG : Process uptime: 0s 03-15 16:21:05.432 7914 7914 F DEBUG : Cmdline: /vendor/bin/hw/android.hardware.audio.service-droidlogic 03-15 16:21:05.432 7914 7914 F DEBUG : pid: 3513, tid: 3513, name: audio.service-d >>> /vendor/bin/hw/android.hardware.audio.service-droidlogic <<< 03-15 16:21:05.432 7914 7914 F DEBUG : uid: 1041 03-15 16:21:05.432 7914 7914 F DEBUG : signal 35 (<debuggerd signal>), code -1 (SI_QUEUE from pid 3579, uid 1041), fault addr -------- 03-15 16:21:05.432 7914 7914 F DEBUG : r0 00000006 r1 c0306201 r2 ff88ce90 r3 ff88cdd4 03-15 16:21:05.432 7914 7914 F DEBUG : r4 f4c1a138 r5 c0306201 r6 ff88ce90 r7 00000036 03-15 16:21:05.432 7914 7914 F DEBUG : r8 f43c0888 r9 f43c0844 r10 f4c1a138 r11 ff88ce90 03-15 16:21:05.432 7914 7914 F DEBUG : ip 00000100 sp ff88cdc0 lr f4bc8cbb pc f4bfaebc 03-15 16:21:05.432 7914 7914 F DEBUG : backtrace: 03-15 16:21:05.432 7914 7914 F DEBUG : #00 pc 00070ebc /apex/com.android.runtime/lib/bionic/libc.so (__ioctl+8) (BuildId: 065f5a7b98a8052e1c4af4e537983a0f) 03-15 16:21:05.432 7914 7914 F DEBUG : #01 pc 0003ecb7 /apex/com.android.runtime/lib/bionic/libc.so (ioctl+26) (BuildId: 065f5a7b98a8052e1c4af4e537983a0f) 03-15 16:21:05.433 7914 7914 F DEBUG : #02 pc 00053315 /apex/com.android.vndk.v31/lib/libhidlbase.so (android::hardware::IPCThreadState::getAndExecuteCommand()+144) (BuildId: 61a23abb570cc7f6a181c54d7bd04c68) 03-15 16:21:05.433 7914 7914 F DEBUG : #03 pc 000531e5 /apex/com.android.vndk.v31/lib/libhidlbase.so (android::hardware::IPCThreadState::joinThreadPool(bool)+56) (BuildId: 61a23abb570cc7f6a181c54d7bd04c68) 03-15 16:21:05.433 7914 7914 F DEBUG : #04 pc 000025fd /vendor/bin/hw/android.hardware.audio.service-droidlogic (main+2468) (BuildId: cee1ecdb908a8f9def6b7234d77457b6) 03-15 16:21:05.433 7914 7914 F DEBUG : #05 pc 00031f9d /apex/com.android.runtime/lib/bionic/libc.so (__libc_init+56) (BuildId: 065f5a7b98a8052e1c4af4e537983a0f) Thanks, Peter |
|
|
Hi Peter, I reproduced this issue as below. 1. Pairing with BA01 RCU 2. Reboot STB 3. Try voice recognition by pressing the NUGU key -> Crash occurs in 2~3 times Please check attached log and tombstone files. Thank you. Kim |
|
|
Hi Peter This issue is urgent. Please check it quickly. Thank you YK.Jung |
|
|
Hi JunGyu, I cannot reproduce this issue with your step so far. Is there any step i need to do else ? Which FW you're using to reproduce it ? From log, NUGU voice is not work after the audio server crashed. Thanks, Peter |
|
|
Hi Peter, I have tested this issue in FW 15.537.24 / 15.537.26 and I can reproduce both FW. I repeated Active NUGU <-> exit NUGU. I also tried voice recognition sometimes. A reproduction video is attached. Please refer it. Thank you. Kim KakaoTalk_20230320_165639313.mp4 (46,085,788 bytes) |
|
|
Hi Peter, Additionally, I attached video that our QA was reproducing this issue. At this video, QA tried Channel up / down / Volume up / down / Mute on. After reboot device, this issue was reproduced. Please refer it. Thank you. Kim Nugu_X_(4h11m).mp4 (38,363,569 bytes) |
|
|
Hi Peter This issue ( priority is major) is continuously being reproduced. Due to the ATV12 schedule, the major issue of ATV12 needs to be resolved quickly. BPM-16462 / BPM-16171 Please check it quickly Thank you YK.Jung |
|
|
Hi Peter This issue is observed only in the FXN model. Please let me know the schedule by when it will be resolved. Thank you YK.Jung |
|
|
Hi YK / JunGyu, According to the video attached, I still cannot reproduce this issue on my side. Can you help to try with the test image and share the log? image path : /release_by_fxn/smart3_test/nugu Thanks, Peter |
|
|
Hi Peter, I have attached the video and log reproduced in the test FW. Please check it. Thank you. Kim Nugu_X_logcat.mp4 (42,982,327 bytes) |
|
|
Hi Peter Additionally, our QA tested in FW 15.537.281 (applying NUGU patch from amlogic) but still reproduced this issue. At this FW, when NUGU recognition does not work, live screen is stopped. I also added video and log file. Thank you, Kim NUGU_X_15.537.281.mp4 (13,784,940 bytes) |
|
|
Hi JunGyu, Please help to try with the test image again and share the log. Path : /release_by_fxn/smart3_test/nugu/k000c-537r29_SD-20230324-BFX-AT100 Thanks, Peter |
|
|
Hi Peter Below is the result of testing in your test FW. 1. The volume is not controlled in AC3 channel by "B tv" setting. 2. After reboot, the first NUGU recognition is not work. From the second, NUGU recognition is work well. (Sometimes second NUGU recognition is NOT work.) I attached two log files. Thank you. Kim |
|
|
Hi JunGyu, From the log, the audio input device is correct and the audio server is not crashed. Can you check it again? 03-27 11:30:19.160 3438 3438 D audio_hw_primary: adev_open_input_stream: enter: devices(0x80000010) channel_mask(0x10) rate(16000) format(0x1) source(20) 03-27 11:30:30.095 3438 3481 D audio_hw_primary: adev_open_input_stream: enter: devices(0x80000010) channel_mask(0x10) rate(16000) format(0x1) source(20) 03-27 11:30:38.131 3438 3481 D audio_hw_primary: adev_open_input_stream: enter: devices(0x80000010) channel_mask(0x10) rate(16000) format(0x1) source(20) Thanks, Peter |
|
|
Hi Peter, I have test it with your FW again and after reboot device, this issue was reproduced. At the log, crash is occurring. Please refer this log. Thank you. Kim |
|
|
Hi JunGyu, 1. Can you help to confirm NUGU is work well before audio server crashed? (From the log, audio input device is correct and NUGU open/close normally before audio server crashed.) 2. Can you try to not playing Live TV when boot up and test again? Thanks, Peter |
|
|
Hi Peter, I have verified the last log, this log is tested in another FW. Please forget this log. (BFX-AT100_20230327-172558.zip) At the result of testing, the crash is not occurring but NUGU recognition is not working first time. I think this issue caused by something else. BTW, I reported two issue. Did you check the log of first issue? (the volume is not controlled in AC3 channel by "B tv" setting) Thank you. Kim |
|
|
Hi JunGyu, Thanks for your confirmation. Can you try to not playing Live TV when boot up and test again? I will check again the result log of testing. I think we can focus on the NUGU issue. Thanks, Peter |
|
|
Hi Peter The following issue were observed during the test with the FW you sent. (/release_by_fxn/smart3_test/nugu/k000c-537r29_SD-20230324-BFX-AT100) When a nugu issue occurs - NUGU function do not work when RCU's NUGU button is pressed - About RCU' LED In this state, the LED on the RCU are not on and are off. (Originally, if user press a NUGU button, the LED should be on for a certain period of time, but the LED turns off immediately when it is in an issue state ) - About GA test at issue state But GA is operating normally. (the GA normally has LEDs on for a certain period of time.) - The same issue is observed when the STB is plug power off and on. - This issue seems to disappear when I re-pair RCU and STB. I'm attaching two log files, so please check it ok case after rebooting : BFX-AT100_20230328-193626_NUGU_ok.zip issue case after rebooting : BFX-AT100_20230329-160318_NUGU_issue.zip Thank you YK.Jung |
|
|
Hi Peter SKT's opinion is that NUGU has no problem when the issue occurs. Please update the progress. Thank you YK.Jung |
|
|
Hi YK, Can you help to check the RCU firmware version? Thanks, Peter |
|
|
Hi Peter This issue is observed in BA01/BA02 RCU. version of BMM BA01 is 02.00 version of BMM BA02 is 1.5 Thanks YK.Jung |
|
|
Hi Peter This issue must be resolved next week. But I know that you have a day off early next week. So please commit the code that you think is stable by today. We will proceed with the additional test with the final Smart3 bitbucket FW. Thank you YK.Jung |
|
|
Hi YK, Sorry, can you share how to check the RCU firmware version? BTW, the test FW I provided before only add some debug logs. Thanks, Peter |
|
|
Hi Peter 1) press * 7 8 9 9 # 2) Please check the attached screen. This is an example screen. the rcu version I tested was 02.00. "리모컨 버젼" : rcu's FW version Thanks you YK.Jung image.png (61,969 bytes) |
|
|
Hi Peter Now this NUGU issue is Major priority. it's a serious situation. please let me know if you have any doubts. We will check it during your day off. Thank you YK.Jung |
|
|
Hi Peter, I have attached the reproduced log from your test FW (15.537.29) Symptoms are the same as youngkwang jung's comment. The log attached this time is the log when the first tombstone occurs. For reference, the RCU version is 02.00. The reproduction scenario is same as the video delivered earlier, Channel up / down, volume up / down -> It occurred after cold booting but the reproducibility is low. At the time of the issue, NUGU is active on the screen, but the green LED on the RCU is not on. Please check this log. Thank you. Kim |
|
|
Hi Peter, I have found some strange things. At the log of today I attached, I pressed NUGU and EXIT key but "snd_atvr_pcm_trigger " is not called. // Normal case 04-06 14:16:18.670 0 0 W : [ 162.652845@2]- key down 194 <<---- input NUGU key 04-06 14:16:18.758 0 0 I [ 162.741549@1]- snd_atvr_pcm_open: 1363 04-06 14:16:18.758 0 0 I [ 162.741558@1]- snd_atvr_pcm_open: 1390 04-06 14:16:18.759 0 0 I [ 162.741614@1]- snd_atvr_pcm_hw_params: 1347 04-06 14:16:18.759 0 0 I [ 162.741656@1]- snd_atvr_pcm_prepare: 1301 04-06 14:16:18.759 0 0 I [ 162.741661@1]- snd_atvr: snd_atvr_pcm_prepare, rate = 16000, period_size = 160, buffer_size = 640 04-06 14:16:18.766 0 0 W [ 162.741722@0]- snd_atvr_pcm_prepare: open mic 04-06 14:16:18.766 0 0 I [ 162.741734@0]d snd_atvr: snd_atvr_pcm_trigger starting audio 04-06 14:16:18.767 0 0 I [ 162.741736@0]d snd_atvr_pcm_trigger: 1257 04-06 14:16:18.767 0 0 I [ 162.741738@0]d snd_atvr_timer_start: 1216 04-06 14:16:22.302 0 0 W : [ 166.284223@1]- key down 174 <<---- input EXIT key 04-06 14:16:22.435 0 0 I [ 166.417573@2]d snd_atvr: snd_atvr_pcm_trigger stopping audio, peak = 1506, # packets = 306 04-06 14:16:22.505 0 0 I [ 166.417581@2]d snd_atvr_timer_stop: 1235 04-06 14:16:22.505 0 0 I [ 166.417589@2]- snd_atvr_pcm_hw_free: 1354 04-06 14:16:22.505 0 0 I : [ 166.417625@2]- snd_atvr_pcm_close 04-06 14:16:22.505 0 0 I [ 166.417628@2]- snd_atvr_timer_stop: 1235 // Abnormal case 04-06 09:54:04.262 0 0 W : [ 55.206567@0]- key down 194 <<---- input NUGU key 04-06 09:54:04.437 0 0 I [ 55.378336@3]- snd_atvr_pcm_open: 1363 04-06 09:54:04.437 0 0 I [ 55.378344@3]- snd_atvr_pcm_open: 1390 04-06 09:54:04.437 0 0 I [ 55.378397@3]- snd_atvr_pcm_hw_params: 1347 04-06 09:54:04.437 0 0 I [ 55.378439@3]- snd_atvr_pcm_prepare: 1301 04-06 09:54:04.437 0 0 I [ 55.378444@3]- snd_atvr: snd_atvr_pcm_prepare, rate = 16000, period_size = 160, buffer_size = 640 04-06 09:54:04.448 0 0 W [ 55.378473@3]- snd_atvr_pcm_prepare: open mic 04-06 09:54:04.448 0 0 I [ 55.378481@3]d snd_atvr: snd_atvr_pcm_trigger starting audio 04-06 09:54:04.448 0 0 I [ 55.378484@3]d snd_atvr_pcm_trigger: 1257 04-06 09:54:04.448 0 0 I [ 55.378485@3]d snd_atvr_timer_start: 1216 04-06 09:54:14.247 0 0 W : [ 65.188344@3]- key down 174 <<---- input EXIT key. At this time, "snd_atvr_pcm_trigger" is not calling. 04-06 09:54:14.968 5713 5713 D UPNSService: [UPNSService] Handling crashed service: true 04-06 09:54:15.115 0 0 W : [ 66.058698@3]- key down 194 04-06 09:54:17.060 0 0 W : [ 68.000758@3]- key down 194 <<---- input NUGU key 04-06 09:54:18.710 0 0 I [ 69.653087@3]d snd_atvr: snd_atvr_pcm_trigger stopping audio, peak = -32768, # packets = 0 04-06 09:54:19.200 0 0 I [ 69.653093@3]d snd_atvr_timer_stop: 1235 <<---- At this time, snd_atvr_pcm_trigger is called. It seems to be called by timer_stop. 04-06 09:54:19.200 0 0 I [ 69.653099@3]- snd_atvr_pcm_hw_free: 1354 04-06 09:54:19.261 0 0 I [ 69.653106@3]- snd_atvr_timer_stop: 1235 I thkin this seems to be the problem, please check it and refer to it when analyzing the log. Thank you. Kim |
|
|
Hi JunGyu, Can you try to use the below test image to check again? Path : /release_by_fxn/smart3_test/nugu/k000c-537r37_SD-20230410-BFX-AT100 Thanks, Peter |
|
|
Hi Peter, I attached log file from test FW when the crash has been occurred. Please check it. Thank you. Kim |
|
|
Hi JunGyu, Can you help to get more log with below steps? 1. adb reboot bootloader fastboot flashing unlock fastboot reboot // need to open adb again manually adb root adb disable-verity adb reboot adb root adb remount adb push bt_stack.conf /system/etc/bluetooth 2. Settings -> Developer options -> Enable Bluetooth HCI snoop log ==> set "enabled" And then reboot device to get the log. Thanks, Peter bt_stack.conf (1,952 bytes) |
|
|
Hi Peter, I attached as you requested logs. Please check it. Thank you Kim |
|
|
Hi Peter, I think I found the issue reproduce step. 1. Pairing RCU 2. Battery off -> on the RCU 3. re-pairing RCU by pressing * + # 4. Check NUGU is working 5. AC off -> ON 6. After booting the STB, press NUGU key, the LED is not on the RCU 7. After some time, the crash is occurriing. As you know that the ATV12 has RCU disconecting issue (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1702) At the log I attached above, RCU is disconnected after reboot. So I re-pairing the RCU. After reboot device, the crash is occurring. I attached the log when RCU is disconnecting. You can check btsnoop log through above log file(20230412_logs/logs/btsnoop_hci.log.last) Please refer it. Thank you. Kim |
|
|
Hi JunGyu, Thanks. I'll check if i can reproduce this issue by your step. Thanks, Peter |
|
|
Hi Peter, Please let me know if any update. Thank you. Kim |
|
|
Hi JunGyu, I cannot reproduce this issue so far, but i will keep to try it. BTW, Please try the test image below Path : /release_by_fxn/smart3_test/nugu/k000c-537r37_SD-20230413-BFX-AT100 Thanks, Peter |
|
|
Hi Peter, It is still being reproduced in the test FW. I attached log file. Thank you Kim |
|
|
Hi JunGyu, Can you help to check with these two ways? 1. type this command and check it adb root adb shell pm disable com.google.android.tv.remote.service 2. check with the test image Path : /release_by_fxn/smart3_test/nugu/k000c-537r39_SD-20230414-BFX-AT100 Thanks, Peter |
|
|
Hi Peter, 1. adb shell pm disable com.google.android.tv.remote.service >> [ALT] I tested both 15.537.38 (release FW) and 15.537.39 (test FW you shared) FW, both FW reproduced same issue after type the command "adb shell pm disable com.google.android.tv.remote.service". 2. check with the test image >> [ALT] It is still being reproduced in the test FW. I attached log file. Additionally, I attached reproduce video. Please refer it. Thank you Kim 20230414_163234.mp4 (89,230,765 bytes) |
|
|
Hi JunGyu, Sorry for the inconvenience, please help to try again with below. 1. type this command and check it adb root adb shell pm uninstall --user 0 -k com.google.android.katniss 2. check with the test image (I have uploaded a new image) Path : /release_by_fxn/smart3_test/nugu/k000c-537r39_SD-20230414-BFX-AT100 Thanks, Peter |
|
|
Hi Peter, 1. The issue is still reproducing after type the command "adb shell pm uninstall --user 0 -k com.google.android.katniss". 2. It is still being reproduced in the test FW. I attached log file. Thank you. Kim |
|
|
Hi Peter This issue has not been resolved for too long. It must be resolved by this week. (4/21) Thank you YK.Jung |
|
|
Hi JunGyu, We try to revert one patch and please help to check again. Path : /release_by_fxn/smart3_test/nugu/k000c-537r39_SD-20230417-BFX-AT100 Thanks, Peter |
|
|
Hi Peter, As a result of checking 20 times with the reproduction method I mentioned, crash does not occur. The patch you reverted seems affect this issue. Can you share what you reverted? Thank you. Kim |
|
|
Hi Peter, Additionally, we need to verify this issue with our QA. But, your FW's voice recognition rate is low. I think the reason is additional log for debug. Please revert and share only the problem patch based on the latest version. I will verify it with our QA. Thank you Kim |
|
|
Hi JunGyu, It seems like we have similar issue long time ago. (https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1152) And we revert the patch "HID cache commit (which is enabled by google from android 10)" to fix it. Thanks, Peter |
|
|
Hi Peter, Thank you for explain. Please share the FW that as I mentioned above. I will test it with our QA. Thank you. Kim |
|
|
Hi JunGyu, Please check it Path : /release_by_fxn/smart3_test/nugu/k000c-537r39_SD-20230418-BFX-AT100 Thanks, Peter |
|
|
Hi Peter, Our QA reproduced NUGU recognition is not working issue with the reproduction method I mentioned in your FW. I verified log and the crash is not occurring. It seems another issue. I attached video and logcat first. Please check it urgently. I will check logcat also. Note that after reboot device, NUGU recognition is working well. Thank you Kim NUGU_X_20230419.mp4 (3,500,914 bytes) |
|
|
Hi JunGyu, Can you help to check the green LED on the RCU is on or not? Thanks, Peter |
|
|
Hi Peter, We are currently retry this issue but the issue is not reproducing. I will let you know if this issue reproduce again. Is there any strange log? BTW, I think the patch "HID cache commit (which is enabled by google from android 10)" must be include because this patch already applied to ATV10. Please commit this patch. Thank you. Kim |
|
|
Hi JunGyu, I don't find any strange log. If you reproduced it again, please check the LED on the RCU and get the fail log. OK, I applied the patch "HID cache commit" on ATV12. Thanks, Peter |
|
|
Hi Peter, I and our QA tested over 100 times but the issue is not reproduced. So I close this issue. If this issue is reproduce, I will reopen this issue. Thank you for the support. Kim |
- yk.jung ( (ALTech) Younkwang Jung ) developer
.png)
